Skip to content

Conversation

@Haarolean
Copy link
Member

  • Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

  • No need to
  • Manually (please, describe, if necessary)
  • Unit checks
  • Integration checks
  • Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
  • My changes generate no new warnings (e.g. Sonar is happy)
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

@Haarolean Haarolean added type/chore Boring stuff, could be refactoring or tech debt impact/documentation A PR with changes which should be addressed in the documentation labels Feb 24, 2025
@Haarolean Haarolean self-assigned this Feb 24, 2025
@Haarolean Haarolean requested a review from a team as a code owner February 24, 2025 12:25
@kapybro kapybro bot added status/triage Issues pending maintainers triage status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Feb 24, 2025
@Haarolean Haarolean merged commit 01c6b69 into main Feb 24, 2025
31 of 34 checks passed
@Haarolean Haarolean deleted the ami--link branch February 24, 2025 19:46
git-halinka pushed a commit to sainsburys-tech/kafka-ui that referenced this pull request Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

impact/documentation A PR with changes which should be addressed in the documentation status/triage/completed Automatic triage completed type/chore Boring stuff, could be refactoring or tech debt

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants